Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d157b62993c5d103fa2d7eac5b14123b972c8080bc51e16bea8bd7a97b72d3

Tx prefix hash: 8366d4ec3fa82d943377de1c2a35056c6439909f69fcb665b79ca16d9bcd6053
Tx public key: 37b5c00f2559b54e5d260dd82c64034ebfbffb534cffff64d8d6470255543cf8
Timestamp: 1709433701 Timestamp [UCT]: 2024-03-03 02:41:41 Age [y:d:h:m:s]: 01:036:23:30:04
Block: 969964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287422 RingCT/type: yes/0
Extra: 0137b5c00f2559b54e5d260dd82c64034ebfbffb534cffff64d8d6470255543cf802110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b8c25430a55d1d97b16f3e3aaa2afb704ab8fcae711c118ca54fae4dde25e3 0.600000000000 1429813 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": 969974, "vin": [ { "gen": { "height": 969964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b8c25430a55d1d97b16f3e3aaa2afb704ab8fcae711c118ca54fae4dde25e3" } } ], "extra": [ 1, 55, 181, 192, 15, 37, 89, 181, 78, 93, 38, 13, 216, 44, 100, 3, 78, 191, 191, 251, 83, 76, 255, 255, 100, 216, 214, 71, 2, 85, 84, 60, 248, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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