Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2e12507f1bdda479232cc5d3d6376979dce8a17adeb2ce12ac39d972da279d

Tx prefix hash: e42d0f969fff85a6ced534a5d294b96fe5c512fb3584f987f332683136708c1c
Tx public key: 6fc8b69040cd8ed15ebcbced45dd277849c52d815845a98af908209207f596d0
Timestamp: 1580479770 Timestamp [UCT]: 2020-01-31 14:09:30 Age [y:d:h:m:s]: 05:030:04:26:55
Block: 55793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173468 RingCT/type: yes/0
Extra: 016fc8b69040cd8ed15ebcbced45dd277849c52d815845a98af908209207f596d0021100000001391a8d0e000000000000000000

1 output(s) for total of 400.991765859000 dcy

stealth address amount amount idx
00: d51ba0fce3484718fda8ce7f89e896a85d402c0b4b2a44e9a58096c46277b93c 400.991765859000 102950 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": 55803, "vin": [ { "gen": { "height": 55793 } } ], "vout": [ { "amount": 400991765859, "target": { "key": "d51ba0fce3484718fda8ce7f89e896a85d402c0b4b2a44e9a58096c46277b93c" } } ], "extra": [ 1, 111, 200, 182, 144, 64, 205, 142, 209, 94, 188, 188, 237, 69, 221, 39, 120, 73, 197, 45, 129, 88, 69, 169, 138, 249, 8, 32, 146, 7, 245, 150, 208, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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