Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a9f895dbcb3c2ee09e00a1b280e3ed8455ad719d5e3a9a09b197cd8b3e4fb2

Tx prefix hash: 5011e5e5c950d33435a30571f8d2e360bd7a3d712676d0c722a35764873c0a9f
Tx public key: 5053bf082fde409014fbe8e7f048c0236ba7eded3a48c9f9c4ebf392d9d7aad5
Timestamp: 1704445738 Timestamp [UCT]: 2024-01-05 09:08:58 Age [y:d:h:m:s]: 01:074:12:25:42
Block: 928584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314391 RingCT/type: yes/0
Extra: 015053bf082fde409014fbe8e7f048c0236ba7eded3a48c9f9c4ebf392d9d7aad502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5410dd1e189cb4bbb52df7a74f56f1b0ffe9cd96642a6552c1ff8b1cbd47f99 0.600000000000 1386444 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": 928594, "vin": [ { "gen": { "height": 928584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5410dd1e189cb4bbb52df7a74f56f1b0ffe9cd96642a6552c1ff8b1cbd47f99" } } ], "extra": [ 1, 80, 83, 191, 8, 47, 222, 64, 144, 20, 251, 232, 231, 240, 72, 192, 35, 107, 167, 237, 237, 58, 72, 201, 249, 196, 235, 243, 146, 217, 215, 170, 213, 2, 17, 0, 0, 0, 4, 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