Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a40501d8c374dffecbf966c47f3d2d513bbf48a26169cc0ed30b43638233c0

Tx prefix hash: 9f62976eda4aa742ffd3c1900b88ecf2ea0dcced62f03155ff053e8094053855
Tx public key: 27ecf22bbfdced2b029cc950f7edfc80ca3d021dbf1e9128e7db82d3045ef84a
Timestamp: 1579038393 Timestamp [UCT]: 2020-01-14 21:46:33 Age [y:d:h:m:s]: 05:292:01:44:36
Block: 45616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1356641 RingCT/type: yes/0
Extra: 0127ecf22bbfdced2b029cc950f7edfc80ca3d021dbf1e9128e7db82d3045ef84a021100000001d81c26c0000000000000000000

1 output(s) for total of 433.367257136000 dcy

stealth address amount amount idx
00: ba4f62c423661df5de953ea29c78f183d70e7ad5577e93068840e98d2c9e80e0 433.367257136000 83444 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": 45626, "vin": [ { "gen": { "height": 45616 } } ], "vout": [ { "amount": 433367257136, "target": { "key": "ba4f62c423661df5de953ea29c78f183d70e7ad5577e93068840e98d2c9e80e0" } } ], "extra": [ 1, 39, 236, 242, 43, 191, 220, 237, 43, 2, 156, 201, 80, 247, 237, 252, 128, 202, 61, 2, 29, 191, 30, 145, 40, 231, 219, 130, 211, 4, 94, 248, 74, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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