Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1582cd8ff0adb7c3a480b26003ba39c1ce414a6d1b0feeae2ae581774023faee

Tx prefix hash: a04581a1533f1d347fbd55001f6a6dc61c594ee264b98f33ffb988f56acfaa72
Tx public key: 860f74738c7ddf5dd789cacfe4b5e1f6a1d215f27ea7ea1f3c6553a180366522
Timestamp: 1737274904 Timestamp [UCT]: 2025-01-19 08:21:44 Age [y:d:h:m:s]: 00:150:13:02:03
Block: 1200588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107318 RingCT/type: yes/0
Extra: 01860f74738c7ddf5dd789cacfe4b5e1f6a1d215f27ea7ea1f3c6553a180366522021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d323253d66780e4509cedfd3c7d64eb6e9126ce4ab3add24af9d0e61864678db 0.600000000000 1687233 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": 1200598, "vin": [ { "gen": { "height": 1200588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d323253d66780e4509cedfd3c7d64eb6e9126ce4ab3add24af9d0e61864678db" } } ], "extra": [ 1, 134, 15, 116, 115, 140, 125, 223, 93, 215, 137, 202, 207, 228, 181, 225, 246, 161, 210, 21, 242, 126, 167, 234, 31, 60, 101, 83, 161, 128, 54, 101, 34, 2, 17, 0, 0, 0, 5, 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