Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4674fb8235692d7188b5a28125bdcf69880645c245912aa8d61e1e8c383bed87

Tx prefix hash: b7e944cc9280471e45334fc097071d5cfe3f56e4039181f246594b06d01ee0b8
Tx public key: a16386c936308e1a5ad8e1dbbf3b0fb725b67bc91190c3260d71cc415c276a65
Timestamp: 1685544645 Timestamp [UCT]: 2023-05-31 14:50:45 Age [y:d:h:m:s]: 02:177:19:12:57
Block: 772154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646875 RingCT/type: yes/0
Extra: 01a16386c936308e1a5ad8e1dbbf3b0fb725b67bc91190c3260d71cc415c276a65021100000007faf35c9c000000000000000000

1 output(s) for total of 1.696420189000 dcy

stealth address amount amount idx
00: d98e7936e34f7be00d787e0f77e7d3d9448f4eaa03a1f6e87a969ff0dfa67787 1.696420189000 1221547 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 772164, "vin": [ { "gen": { "height": 772154 } } ], "vout": [ { "amount": 1696420189, "target": { "key": "d98e7936e34f7be00d787e0f77e7d3d9448f4eaa03a1f6e87a969ff0dfa67787" } } ], "extra": [ 1, 161, 99, 134, 201, 54, 48, 142, 26, 90, 216, 225, 219, 191, 59, 15, 183, 37, 182, 123, 201, 17, 144, 195, 38, 13, 113, 204, 65, 92, 39, 106, 101, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8