Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa85d06d64d036fb610f076bf1e160ae497af64f0c914ebad6406da56ebd9939

Tx prefix hash: a10040c8791206e693132948e18710ad07de244f5ac66dda3541fb6c0e7acbde
Tx public key: 240c13b78a7971d6d82a8c0241fbd47ccbeea0a46fc86bd43f32437347e4beb0
Timestamp: 1715097037 Timestamp [UCT]: 2024-05-07 15:50:37 Age [y:d:h:m:s]: 00:136:20:48:25
Block: 1016907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98046 RingCT/type: yes/0
Extra: 01240c13b78a7971d6d82a8c0241fbd47ccbeea0a46fc86bd43f32437347e4beb002110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e2b7c3776aee354fff34d39c486d39b58733ae5b79e4a0ddec69e3bfbc31f2 0.600000000000 1480632 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": 1016917, "vin": [ { "gen": { "height": 1016907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e2b7c3776aee354fff34d39c486d39b58733ae5b79e4a0ddec69e3bfbc31f2" } } ], "extra": [ 1, 36, 12, 19, 183, 138, 121, 113, 214, 216, 42, 140, 2, 65, 251, 212, 124, 203, 238, 160, 164, 111, 200, 107, 212, 63, 50, 67, 115, 71, 228, 190, 176, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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