Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6bd0e99dd1cae3c4590dbbbb1efef819c247f0fdc0952a0b1fc962fa8560f4

Tx prefix hash: 0554477a7192d0fbf66548161595bece12f891c6fa6807137018fc54d50b5867
Tx public key: 2ed0dda54da24d0adceb2f26c8d763afda5f5069ea0864d0d62787fc788fc9ed
Timestamp: 1729727190 Timestamp [UCT]: 2024-10-23 23:46:30 Age [y:d:h:m:s]: 00:031:13:59:53
Block: 1138169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22557 RingCT/type: yes/0
Extra: 012ed0dda54da24d0adceb2f26c8d763afda5f5069ea0864d0d62787fc788fc9ed021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3632b088d3f031c43e815a0c60a054d1c8cb6f6c887dddf17c7012f3b656fa07 0.600000000000 1621786 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": 1138179, "vin": [ { "gen": { "height": 1138169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3632b088d3f031c43e815a0c60a054d1c8cb6f6c887dddf17c7012f3b656fa07" } } ], "extra": [ 1, 46, 208, 221, 165, 77, 162, 77, 10, 220, 235, 47, 38, 200, 215, 99, 175, 218, 95, 80, 105, 234, 8, 100, 208, 214, 39, 135, 252, 120, 143, 201, 237, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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