Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6155206094db8bf7b0af21c69f7b9d8d4fe3118e50a0a967b248354a75c42be2

Tx prefix hash: 2172692d63f2cb51240a755b52f0419d3e603852d45688e01288d67e3534bde2
Tx public key: ce0a44ac38a1be104f06ef98e861392e5f4a2b769591a888cd0c093d1b68f022
Timestamp: 1582387098 Timestamp [UCT]: 2020-02-22 15:58:18 Age [y:d:h:m:s]: 04:257:20:40:41
Block: 70308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076775 RingCT/type: yes/0
Extra: 01ce0a44ac38a1be104f06ef98e861392e5f4a2b769591a888cd0c093d1b68f0220211000000017adf42d3000000000000000000

1 output(s) for total of 358.955996666000 dcy

stealth address amount amount idx
00: 01faf86e889681b069d16f40a2c4818ec455acd86ef340ff4c6d5cdee618c559 358.955996666000 129855 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": 70318, "vin": [ { "gen": { "height": 70308 } } ], "vout": [ { "amount": 358955996666, "target": { "key": "01faf86e889681b069d16f40a2c4818ec455acd86ef340ff4c6d5cdee618c559" } } ], "extra": [ 1, 206, 10, 68, 172, 56, 161, 190, 16, 79, 6, 239, 152, 232, 97, 57, 46, 95, 74, 43, 118, 149, 145, 168, 136, 205, 12, 9, 61, 27, 104, 240, 34, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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