Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64ae4cf637b1c28b41b0839d30b338c2ba3b59d99d2700601e7d6720a0515d0

Tx prefix hash: b51d3f7b41f9218d337fb7fe874275880757c9a0dc15aded95ad9c459a90b877
Tx public key: da485f4f1b3e9a8de1eb97b5b3d6e58d45ec75c5d779e12a769b8cd797834ac4
Timestamp: 1699491941 Timestamp [UCT]: 2023-11-09 01:05:41 Age [y:d:h:m:s]: 01:152:11:18:27
Block: 887543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370159 RingCT/type: yes/0
Extra: 01da485f4f1b3e9a8de1eb97b5b3d6e58d45ec75c5d779e12a769b8cd797834ac402110000000233af99f4000000000000000000

1 output(s) for total of 0.703398772000 dcy

stealth address amount amount idx
00: c2ca7ef9fd814c412dda88a373ad427081c1d9896efb1f41556df0537e65c8e1 0.703398772000 1343428 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": 887553, "vin": [ { "gen": { "height": 887543 } } ], "vout": [ { "amount": 703398772, "target": { "key": "c2ca7ef9fd814c412dda88a373ad427081c1d9896efb1f41556df0537e65c8e1" } } ], "extra": [ 1, 218, 72, 95, 79, 27, 62, 154, 141, 225, 235, 151, 181, 179, 214, 229, 141, 69, 236, 117, 197, 215, 121, 225, 42, 118, 155, 140, 215, 151, 131, 74, 196, 2, 17, 0, 0, 0, 2, 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