Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5cdd4aed0600067a286533a63a790184e5fa2c5fdf41c899fab003a1dd630a6

Tx prefix hash: e9a17fc33aaf5de52fc61e0c7d52a95872ec764b2fb5e43655fcf4b179afefc0
Tx public key: 82e97f8bfb220a1a47b48571dbd46a1fd936bf8b296945f03fd0be7056e4c333
Timestamp: 1723505218 Timestamp [UCT]: 2024-08-12 23:26:58 Age [y:d:h:m:s]: 00:216:12:47:11
Block: 1086614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154650 RingCT/type: yes/0
Extra: 0182e97f8bfb220a1a47b48571dbd46a1fd936bf8b296945f03fd0be7056e4c333021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcedbefc1bcb003788fe18e344a7ab2972ba19d13c3e7cfb2b128180a7f86bdd 0.600000000000 1561211 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": 1086624, "vin": [ { "gen": { "height": 1086614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcedbefc1bcb003788fe18e344a7ab2972ba19d13c3e7cfb2b128180a7f86bdd" } } ], "extra": [ 1, 130, 233, 127, 139, 251, 34, 10, 26, 71, 180, 133, 113, 219, 212, 106, 31, 217, 54, 191, 139, 41, 105, 69, 240, 63, 208, 190, 112, 86, 228, 195, 51, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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