Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 134f3747f1a6f1b1161b3dd43378f7ef35703f2feba0b2ab794c90eb5466c016

Tx prefix hash: a9267e45a8cdd487c757d1d63703ea442f2bb9f476ae846ca81926dcc238771e
Tx public key: 1f2fc2b1f57726c165092b114fa0440ba87693a1eb34b9fbc54f9ad4c528677d
Timestamp: 1762842284 Timestamp [UCT]: 2025-11-11 06:24:44 Age [y:d:h:m:s]: 00:081:13:11:55
Block: 1409607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58220 RingCT/type: yes/0
Extra: 011f2fc2b1f57726c165092b114fa0440ba87693a1eb34b9fbc54f9ad4c528677d021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0394cc02dafcfd6728e69a531ca7e3060f0b75ac72c44d9e0f2a583dd5db75ff 0.600000000000 1898054 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": 1409617, "vin": [ { "gen": { "height": 1409607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0394cc02dafcfd6728e69a531ca7e3060f0b75ac72c44d9e0f2a583dd5db75ff" } } ], "extra": [ 1, 31, 47, 194, 177, 245, 119, 38, 193, 101, 9, 43, 17, 79, 160, 68, 11, 168, 118, 147, 161, 235, 52, 185, 251, 197, 79, 154, 212, 197, 40, 103, 125, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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