Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea962dbf889b1484f5c39e94f5597307bf7b148e0705a34e1b133804fbf61b00

Tx prefix hash: e0db4eb8f577a59125eccc6299f13d46c71ac25e4135e35c0b9ea4e34c5a5803
Tx public key: f95bd8b7fe3775ed9f042c86e1ae890d91ffedf68d9c017b85a2e5c87962a431
Timestamp: 1763919347 Timestamp [UCT]: 2025-11-23 17:35:47 Age [y:d:h:m:s]: 00:003:17:51:45
Block: 1418540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2685 RingCT/type: yes/0
Extra: 01f95bd8b7fe3775ed9f042c86e1ae890d91ffedf68d9c017b85a2e5c87962a431021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63db40aad2c811745b87eeaa060ba35d326b00f7e290b3018373032f9230eec0 0.600000000000 1907073 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": 1418550, "vin": [ { "gen": { "height": 1418540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63db40aad2c811745b87eeaa060ba35d326b00f7e290b3018373032f9230eec0" } } ], "extra": [ 1, 249, 91, 216, 183, 254, 55, 117, 237, 159, 4, 44, 134, 225, 174, 137, 13, 145, 255, 237, 246, 141, 156, 1, 123, 133, 162, 229, 200, 121, 98, 164, 49, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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