Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4abc7be5de07f584691fb3bb071580c907a5dd8b7b441bb2e3ab289bad144820

Tx prefix hash: 67759fb39e2e6eb63752fdd80fe68d66b608ebffb923fda9ce2ec19063c65e82
Tx public key: 5883f7fd46c3d1b47dae954630f59f6ef9c91dcde414fe7edbbed585724ff20c
Timestamp: 1631563592 Timestamp [UCT]: 2021-09-13 20:06:32 Age [y:d:h:m:s]: 03:073:16:06:19
Block: 333143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828252 RingCT/type: yes/0
Extra: 015883f7fd46c3d1b47dae954630f59f6ef9c91dcde414fe7edbbed585724ff20c02110000003d5d7cc334000000000000000000

1 output(s) for total of 48.323612007000 dcy

stealth address amount amount idx
00: cdec564f2821b88c57742ff2bad982c93a0ab930608957a3b8d683615fe80ca4 48.323612007000 687598 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": 333153, "vin": [ { "gen": { "height": 333143 } } ], "vout": [ { "amount": 48323612007, "target": { "key": "cdec564f2821b88c57742ff2bad982c93a0ab930608957a3b8d683615fe80ca4" } } ], "extra": [ 1, 88, 131, 247, 253, 70, 195, 209, 180, 125, 174, 149, 70, 48, 245, 159, 110, 249, 201, 29, 205, 228, 20, 254, 126, 219, 190, 213, 133, 114, 79, 242, 12, 2, 17, 0, 0, 0, 61, 93, 124, 195, 52, 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