Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029c637fbd1aeafe9ac97793d8fac564522a883be704484fbe92e5817856bf37

Tx prefix hash: 2698b1d04ba32c2a3cbbbcad8f1ad470c0944fb89b73f6f8542f0ca29eeb5743
Tx public key: bb6833bb403799642677eba6d9305a1cfd2a43aed64b7ebc6e58a0272744e7d0
Timestamp: 1713209085 Timestamp [UCT]: 2024-04-15 19:24:45 Age [y:d:h:m:s]: 01:048:05:40:53
Block: 1001235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295474 RingCT/type: yes/0
Extra: 01bb6833bb403799642677eba6d9305a1cfd2a43aed64b7ebc6e58a0272744e7d0021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40f5a90b8cf3e6ab653b30fbb3b540bce30b8331f3e786e439f0f22dc79b7a78 0.600000000000 1461739 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": 1001245, "vin": [ { "gen": { "height": 1001235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40f5a90b8cf3e6ab653b30fbb3b540bce30b8331f3e786e439f0f22dc79b7a78" } } ], "extra": [ 1, 187, 104, 51, 187, 64, 55, 153, 100, 38, 119, 235, 166, 217, 48, 90, 28, 253, 42, 67, 174, 214, 75, 126, 188, 110, 88, 160, 39, 39, 68, 231, 208, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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