Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f782d6e95cadd3f357b66efc4cf839b067e0e57259be206f053473d9c316149b

Tx prefix hash: 34d7f4c0d53e0f5abe414fafcb7ac050422f695180bc603d879a14074c99ac15
Tx public key: 871259862a0cc3aef85e492092ef708abfcc576b5096348a917ecc68d6a217c3
Timestamp: 1729908287 Timestamp [UCT]: 2024-10-26 02:04:47 Age [y:d:h:m:s]: 00:149:19:38:40
Block: 1139667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106856 RingCT/type: yes/0
Extra: 01871259862a0cc3aef85e492092ef708abfcc576b5096348a917ecc68d6a217c3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10ab0b7b5a555ece3ff3b47ad2d5abc3c985945c029b9e1a0e664e7a38a2a076 0.600000000000 1623454 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": 1139677, "vin": [ { "gen": { "height": 1139667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10ab0b7b5a555ece3ff3b47ad2d5abc3c985945c029b9e1a0e664e7a38a2a076" } } ], "extra": [ 1, 135, 18, 89, 134, 42, 12, 195, 174, 248, 94, 73, 32, 146, 239, 112, 138, 191, 204, 87, 107, 80, 150, 52, 138, 145, 126, 204, 104, 214, 162, 23, 195, 2, 17, 0, 0, 0, 1, 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