Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0890b82617fd232dc550bd339a9aa44f9f3f997fe83c035c04a5830e255433

Tx prefix hash: c96361bc061f83c347cd135a628bf0c883b15965b48271f376ef3196efef5bfc
Tx public key: 91311bcecdbfcd3e6a43c6c814d9ff130cd37122b23b26fe7c63c1206295d78f
Timestamp: 1577822437 Timestamp [UCT]: 2019-12-31 20:00:37 Age [y:d:h:m:s]: 05:016:06:58:15
Block: 35986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161616 RingCT/type: yes/0
Extra: 0191311bcecdbfcd3e6a43c6c814d9ff130cd37122b23b26fe7c63c1206295d78f0211000000098a2ee0d9000000000000000000

1 output(s) for total of 466.406180767000 dcy

stealth address amount amount idx
00: bb8e8ddeca870bee74d841c46dae157963e3de5b56e663699e1ac66423c6b9cb 466.406180767000 60794 of 0

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": 35996, "vin": [ { "gen": { "height": 35986 } } ], "vout": [ { "amount": 466406180767, "target": { "key": "bb8e8ddeca870bee74d841c46dae157963e3de5b56e663699e1ac66423c6b9cb" } } ], "extra": [ 1, 145, 49, 27, 206, 205, 191, 205, 62, 106, 67, 198, 200, 20, 217, 255, 19, 12, 211, 113, 34, 178, 59, 38, 254, 124, 99, 193, 32, 98, 149, 215, 143, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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