Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3d8da164d605a531e89904390132746b6efe693a9dfd4f2bb7b93e99e2d13d

Tx prefix hash: 002e767ebdef915794544145ff52d3e7fc5f96a022097ea6051823693104d72d
Tx public key: d34d8aac43a1ca65b1ae15112d4fc240f0cab842bad64231bb1325424ed1c7e4
Timestamp: 1676608301 Timestamp [UCT]: 2023-02-17 04:31:41 Age [y:d:h:m:s]: 01:312:10:24:27
Block: 698700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484244 RingCT/type: yes/0
Extra: 01d34d8aac43a1ca65b1ae15112d4fc240f0cab842bad64231bb1325424ed1c7e402110000000174b6d784000000000000000000

1 output(s) for total of 2.971096591000 dcy

stealth address amount amount idx
00: 10597f330aaac68f3fac1c502fc1f3ec1812974b99db7b57e8e6d983a671c891 2.971096591000 1142043 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": 698710, "vin": [ { "gen": { "height": 698700 } } ], "vout": [ { "amount": 2971096591, "target": { "key": "10597f330aaac68f3fac1c502fc1f3ec1812974b99db7b57e8e6d983a671c891" } } ], "extra": [ 1, 211, 77, 138, 172, 67, 161, 202, 101, 177, 174, 21, 17, 45, 79, 194, 64, 240, 202, 184, 66, 186, 214, 66, 49, 187, 19, 37, 66, 78, 209, 199, 228, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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