Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7891fba74c086977f31e54f763013f82e93bc35759b0e29cbc7f49b069a3c447

Tx prefix hash: 260bc1a3ae09ab36048f4e7ea5b3d1a96f3480233ba63156930a032f124b0be6
Tx public key: 798bcd0311557faaf1b0e6f336a15f046e3e26b773db9e8a347c8b48578eb616
Timestamp: 1732894386 Timestamp [UCT]: 2024-11-29 15:33:06 Age [y:d:h:m:s]: 00:112:08:01:44
Block: 1164356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80086 RingCT/type: yes/0
Extra: 01798bcd0311557faaf1b0e6f336a15f046e3e26b773db9e8a347c8b48578eb616021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7366681a079836256f0bea81fd1094a3179988bd3815f7ed0b4910108dd34d 0.600000000000 1650029 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": 1164366, "vin": [ { "gen": { "height": 1164356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7366681a079836256f0bea81fd1094a3179988bd3815f7ed0b4910108dd34d" } } ], "extra": [ 1, 121, 139, 205, 3, 17, 85, 127, 170, 241, 176, 230, 243, 54, 161, 95, 4, 110, 62, 38, 183, 115, 219, 158, 138, 52, 124, 139, 72, 87, 142, 182, 22, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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