Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5ae9aa6fd379a1c47d75003e80851d1fcfba2f8b894a987f5f9cfa1ab23e09

Tx prefix hash: 098727504c2b2cd2971cf3823acc4106ae073b1c3816e03ca4c3087ba383846d
Tx public key: a1479d41f82375e55f82bbb59385f79dae82160e198d804194a07f3d0dce3c1d
Timestamp: 1709164791 Timestamp [UCT]: 2024-02-28 23:59:51 Age [y:d:h:m:s]: 01:109:17:32:39
Block: 967731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339371 RingCT/type: yes/0
Extra: 01a1479d41f82375e55f82bbb59385f79dae82160e198d804194a07f3d0dce3c1d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41eca36438c6861edb9e90b5716a8aec2a8a67c73ac101b1cba1e13721ff27d6 0.600000000000 1427516 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": 967741, "vin": [ { "gen": { "height": 967731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41eca36438c6861edb9e90b5716a8aec2a8a67c73ac101b1cba1e13721ff27d6" } } ], "extra": [ 1, 161, 71, 157, 65, 248, 35, 117, 229, 95, 130, 187, 181, 147, 133, 247, 157, 174, 130, 22, 14, 25, 141, 128, 65, 148, 160, 127, 61, 13, 206, 60, 29, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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