Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b12eb935898ff839665c2e12faa2d26fb9f1b57dd057b62b5aa86b3f1e4d959

Tx prefix hash: b23c9733a5ecdb5399caffb0f5299ec73315d69e68568d2b7be7ff15dcde20d3
Tx public key: ea4d06364a95c69246f5917d1d64d7be8c2c617a07917e51f9d6224934dc1d06
Timestamp: 1722079300 Timestamp [UCT]: 2024-07-27 11:21:40 Age [y:d:h:m:s]: 00:254:13:45:36
Block: 1074794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181836 RingCT/type: yes/0
Extra: 01ea4d06364a95c69246f5917d1d64d7be8c2c617a07917e51f9d6224934dc1d0602110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4b9bc3deb7f5c9380d1811ab71d1bf9348c6039680cdcf75804a1b601c0f68f 0.600000000000 1547313 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": 1074804, "vin": [ { "gen": { "height": 1074794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4b9bc3deb7f5c9380d1811ab71d1bf9348c6039680cdcf75804a1b601c0f68f" } } ], "extra": [ 1, 234, 77, 6, 54, 74, 149, 198, 146, 70, 245, 145, 125, 29, 100, 215, 190, 140, 44, 97, 122, 7, 145, 126, 81, 249, 214, 34, 73, 52, 220, 29, 6, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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