Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acb5a5816c14a696557340f01d70c1174671d40f14a8c5b0f7ccce361fc56806

Tx prefix hash: bb9fc110a26302e22a53af9a5a6b08e29f4a3e154925f66894b1b2c2039fe198
Tx public key: acd9d28a6292de934859aba752aad681eb75c365fee3fb97eaf970c0e4802cc9
Timestamp: 1672992801 Timestamp [UCT]: 2023-01-06 08:13:21 Age [y:d:h:m:s]: 02:023:15:38:02
Block: 668712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538555 RingCT/type: yes/0
Extra: 01acd9d28a6292de934859aba752aad681eb75c365fee3fb97eaf970c0e4802cc902110000000833af99f4000000000000000000

1 output(s) for total of 3.734904552000 dcy

stealth address amount amount idx
00: e914eb41276902e884c6f74ea34b5f1c67e87822408b2ad5de9ae4e13396a604 3.734904552000 1109971 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": 668722, "vin": [ { "gen": { "height": 668712 } } ], "vout": [ { "amount": 3734904552, "target": { "key": "e914eb41276902e884c6f74ea34b5f1c67e87822408b2ad5de9ae4e13396a604" } } ], "extra": [ 1, 172, 217, 210, 138, 98, 146, 222, 147, 72, 89, 171, 167, 82, 170, 214, 129, 235, 117, 195, 101, 254, 227, 251, 151, 234, 249, 112, 192, 228, 128, 44, 201, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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