Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0757f810395f591b2075e916fdf087d7be637b99e4679853256768372711a0af

Tx prefix hash: facaca68a7bfd31cb2a1a98372e3af0450f94a80860f0894726f37476d5d5aaf
Tx public key: 89397868f8238bda6e34bf9cec3433c29b66fb54acb9086113c93a98c3bcdfee
Timestamp: 1617117553 Timestamp [UCT]: 2021-03-30 15:19:13 Age [y:d:h:m:s]: 03:271:18:19:44
Block: 229788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953715 RingCT/type: yes/0
Extra: 0189397868f8238bda6e34bf9cec3433c29b66fb54acb9086113c93a98c3bcdfee02110000000e9c1fbdcc000000000000000000

1 output(s) for total of 106.320631722000 dcy

stealth address amount amount idx
00: a2db317e1c545e3d1a47a0982dc2637bc93a38578a15e45a85530aceea4d663e 106.320631722000 476864 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": 229798, "vin": [ { "gen": { "height": 229788 } } ], "vout": [ { "amount": 106320631722, "target": { "key": "a2db317e1c545e3d1a47a0982dc2637bc93a38578a15e45a85530aceea4d663e" } } ], "extra": [ 1, 137, 57, 120, 104, 248, 35, 139, 218, 110, 52, 191, 156, 236, 52, 51, 194, 155, 102, 251, 84, 172, 185, 8, 97, 19, 201, 58, 152, 195, 188, 223, 238, 2, 17, 0, 0, 0, 14, 156, 31, 189, 204, 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