Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215ef33e383ad397f470e9bd2a1774cd3dcdfd39cb2f082f2dacedd4e8ac8ad7

Tx prefix hash: 92a09e6a8ccb27bd79a10f565c85e6ac1b68641b6127a1ee2004975e6bf67fae
Tx public key: 1e5cef04864f101512b1c4c98759ae804c1f3aa19cf309addea7d87375643820
Timestamp: 1741971821 Timestamp [UCT]: 2025-03-14 17:03:41 Age [y:d:h:m:s]: 00:290:09:12:27
Block: 1239259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205313 RingCT/type: yes/0
Extra: 011e5cef04864f101512b1c4c98759ae804c1f3aa19cf309addea7d87375643820021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70abf96605d46448b604075b92958dede3d1d7e3e5456b29353abbff74e7c7c 0.600000000000 1726224 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": 1239269, "vin": [ { "gen": { "height": 1239259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70abf96605d46448b604075b92958dede3d1d7e3e5456b29353abbff74e7c7c" } } ], "extra": [ 1, 30, 92, 239, 4, 134, 79, 16, 21, 18, 177, 196, 201, 135, 89, 174, 128, 76, 31, 58, 161, 156, 243, 9, 173, 222, 167, 216, 115, 117, 100, 56, 32, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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