Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28582bde1df1493fab4e664351e76f199f8fe6855f22e4644c93194507d4916f

Tx prefix hash: 8b598cb2aa3178d43db612be1e9b5ad5066418a1cac2a0763d2a307162b6fdc6
Tx public key: 3a7ca97ccd85e8c09f5614b4ad15c4023245609bbd97ab256f89545c2d9a489f
Timestamp: 1719985236 Timestamp [UCT]: 2024-07-03 05:40:36 Age [y:d:h:m:s]: 00:281:02:48:15
Block: 1057431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200863 RingCT/type: yes/0
Extra: 013a7ca97ccd85e8c09f5614b4ad15c4023245609bbd97ab256f89545c2d9a489f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b9035962bcba17023d1f6f4eb11e5412b9a3d3a5ffdf74b2b0245d2f2cdea03 0.600000000000 1527866 of 15

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": 1057441, "vin": [ { "gen": { "height": 1057431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b9035962bcba17023d1f6f4eb11e5412b9a3d3a5ffdf74b2b0245d2f2cdea03" } } ], "extra": [ 1, 58, 124, 169, 124, 205, 133, 232, 192, 159, 86, 20, 180, 173, 21, 196, 2, 50, 69, 96, 155, 189, 151, 171, 37, 111, 137, 84, 92, 45, 154, 72, 159, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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