Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0abd8a1a0acebbd7512aa1d16e3a7733c4f50991470ee56fbe46b9f80473292

Tx prefix hash: bcbebc2df255890c340cb1605be0a951ec2c3c8dd269588a475823a093235d9e
Tx public key: 55228a4d0b14072ad21d3bbe825ddf619c3028c11f49f8d5142014c92785fcd0
Timestamp: 1625402913 Timestamp [UCT]: 2021-07-04 12:48:33 Age [y:d:h:m:s]: 04:097:04:56:26
Block: 288145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097457 RingCT/type: yes/0
Extra: 0155228a4d0b14072ad21d3bbe825ddf619c3028c11f49f8d5142014c92785fcd002110000001a14aef7b9000000000000000000

1 output(s) for total of 68.120966130000 dcy

stealth address amount amount idx
00: 1244e634987bd2c0a913beceec23a8773a3a83694f897eb966063dbef34c2be6 68.120966130000 603730 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": 288155, "vin": [ { "gen": { "height": 288145 } } ], "vout": [ { "amount": 68120966130, "target": { "key": "1244e634987bd2c0a913beceec23a8773a3a83694f897eb966063dbef34c2be6" } } ], "extra": [ 1, 85, 34, 138, 77, 11, 20, 7, 42, 210, 29, 59, 190, 130, 93, 223, 97, 156, 48, 40, 193, 31, 73, 248, 213, 20, 32, 20, 201, 39, 133, 252, 208, 2, 17, 0, 0, 0, 26, 20, 174, 247, 185, 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