Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4803befe491ca2e442ee4c583dd565272513d708c6b1511b08c200e17e1c5d1f

Tx prefix hash: aa1d5efc6c77bb1dca6abc8209e2b9ad056769cb28b72b2e58e23ec560175534
Tx public key: 77392525c90a5063e115f960e92d91b06d66e9e36da9a225b2c7a525dc100ffa
Timestamp: 1736212661 Timestamp [UCT]: 2025-01-07 01:17:41 Age [y:d:h:m:s]: 00:106:14:21:58
Block: 1191825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75984 RingCT/type: yes/0
Extra: 0177392525c90a5063e115f960e92d91b06d66e9e36da9a225b2c7a525dc100ffa021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ac718de6f0d3331dac84e243361e4c91d8bf433d6b4364780c80c117a0363f6 0.600000000000 1678368 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": 1191835, "vin": [ { "gen": { "height": 1191825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ac718de6f0d3331dac84e243361e4c91d8bf433d6b4364780c80c117a0363f6" } } ], "extra": [ 1, 119, 57, 37, 37, 201, 10, 80, 99, 225, 21, 249, 96, 233, 45, 145, 176, 109, 102, 233, 227, 109, 169, 162, 37, 178, 199, 165, 37, 220, 16, 15, 250, 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