Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb847f9e023c3fd7af6b655c850ba4a18cfa3b70379a87ab17a9006faa442675

Tx prefix hash: 2a920535d4496743eeef720a71dd6022268cb1a29b703e508749c8e644669ebc
Tx public key: 5436dc3b851044eacb55d61605d5efdefa17f0855ebae40b8fbdfd72bd6c55cf
Timestamp: 1708023329 Timestamp [UCT]: 2024-02-15 18:55:29 Age [y:d:h:m:s]: 01:087:17:47:26
Block: 958256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323769 RingCT/type: yes/0
Extra: 015436dc3b851044eacb55d61605d5efdefa17f0855ebae40b8fbdfd72bd6c55cf02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a481c6f91f3fab8a7194a1be034bcc517ea5ae3ee0408cbf41cadf7ec06cd2 0.600000000000 1417615 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": 958266, "vin": [ { "gen": { "height": 958256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a481c6f91f3fab8a7194a1be034bcc517ea5ae3ee0408cbf41cadf7ec06cd2" } } ], "extra": [ 1, 84, 54, 220, 59, 133, 16, 68, 234, 203, 85, 214, 22, 5, 213, 239, 222, 250, 23, 240, 133, 94, 186, 228, 11, 143, 189, 253, 114, 189, 108, 85, 207, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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