Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6785fc88f81d2dc239c2831b50f4450d46ea3e89db35246add85d6b1c57073a7

Tx prefix hash: a80f27da7d9e189ca7c3871ab742c3a7b48de9f6ea7783e143c3e32e33be08d1
Tx public key: 37dd483aa6b0546b1d7244be74b00ab100a8f8d449299326e7eba73cb02ad8ce
Timestamp: 1712962252 Timestamp [UCT]: 2024-04-12 22:50:52 Age [y:d:h:m:s]: 00:350:04:08:01
Block: 999185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250365 RingCT/type: yes/0
Extra: 0137dd483aa6b0546b1d7244be74b00ab100a8f8d449299326e7eba73cb02ad8ce0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baec3ba7f62e0ed56215d6bc4dbb735a28aac37d4addd771d13edad517cdda71 0.600000000000 1459663 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": 999195, "vin": [ { "gen": { "height": 999185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baec3ba7f62e0ed56215d6bc4dbb735a28aac37d4addd771d13edad517cdda71" } } ], "extra": [ 1, 55, 221, 72, 58, 166, 176, 84, 107, 29, 114, 68, 190, 116, 176, 10, 177, 0, 168, 248, 212, 73, 41, 147, 38, 231, 235, 167, 60, 176, 42, 216, 206, 2, 17, 0, 0, 0, 2, 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