Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf912783442b5a391ca97b5505685bb114c3cef6a970e4dc44b8ac260d89962f

Tx prefix hash: 4de03ece17e947d86e2f05327170447270d76b4c4f9a89a672ea505f19009451
Tx public key: e17f9cea8f2150184f168b0c5c860b500961ae526a570eeb1aa8a07aab20337b
Timestamp: 1710447783 Timestamp [UCT]: 2024-03-14 20:23:03 Age [y:d:h:m:s]: 01:240:06:25:21
Block: 978378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430413 RingCT/type: yes/0
Extra: 01e17f9cea8f2150184f168b0c5c860b500961ae526a570eeb1aa8a07aab20337b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52e17fcd07c16b1fed8238cee7eda7c0a6503e0346ae1446d49b4de2a3ef390b 0.600000000000 1438403 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": 978388, "vin": [ { "gen": { "height": 978378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52e17fcd07c16b1fed8238cee7eda7c0a6503e0346ae1446d49b4de2a3ef390b" } } ], "extra": [ 1, 225, 127, 156, 234, 143, 33, 80, 24, 79, 22, 139, 12, 92, 134, 11, 80, 9, 97, 174, 82, 106, 87, 14, 235, 26, 168, 160, 122, 171, 32, 51, 123, 2, 17, 0, 0, 0, 4, 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