Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ab8e78cb48e38d68ccbc099e29187d5e296e287811d5f774857e5bd1736f238

Tx prefix hash: 23613292a431b405319a49cfddb48bca67a193c160c62bd45fdb0ddcb3119f45
Tx public key: deb14386c8028443d8ee7c336f2df2065ad8abdf2758e0fc986b6d73f7f93fbd
Timestamp: 1723450064 Timestamp [UCT]: 2024-08-12 08:07:44 Age [y:d:h:m:s]: 00:254:17:34:58
Block: 1086159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181941 RingCT/type: yes/0
Extra: 01deb14386c8028443d8ee7c336f2df2065ad8abdf2758e0fc986b6d73f7f93fbd02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56578cbdb5ecc8a95e0f80cc197a7a195fbdee743e18dc7c9bae229a277b556f 0.600000000000 1560752 of 15

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": 1086169, "vin": [ { "gen": { "height": 1086159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56578cbdb5ecc8a95e0f80cc197a7a195fbdee743e18dc7c9bae229a277b556f" } } ], "extra": [ 1, 222, 177, 67, 134, 200, 2, 132, 67, 216, 238, 124, 51, 111, 45, 242, 6, 90, 216, 171, 223, 39, 88, 224, 252, 152, 107, 109, 115, 247, 249, 63, 189, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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