Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4704ed36d3bfaf552dee54c3fc4480a9a0af32572f219d7fb6406646d0feb6a8

Tx prefix hash: 574b6bf7f6ff0878444d9a3a7909f2e15c6d9bf5f19ac9a24afe5556a9187cce
Tx public key: a919f9450c25dd854616f8a42311e3f53f67829c7f718a73bbf49b35dc6bb96e
Timestamp: 1765357307 Timestamp [UCT]: 2025-12-10 09:01:47 Age [y:d:h:m:s]: 00:028:03:03:57
Block: 1430449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20157 RingCT/type: yes/0
Extra: 01a919f9450c25dd854616f8a42311e3f53f67829c7f718a73bbf49b35dc6bb96e02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f271678f9a3ebbb79304f5a69c3168094458e5f986e5b16bfd70e0fa7fc18232 0.600000000000 1919200 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": 1430459, "vin": [ { "gen": { "height": 1430449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f271678f9a3ebbb79304f5a69c3168094458e5f986e5b16bfd70e0fa7fc18232" } } ], "extra": [ 1, 169, 25, 249, 69, 12, 37, 221, 133, 70, 22, 248, 164, 35, 17, 227, 245, 63, 103, 130, 156, 127, 113, 138, 115, 187, 244, 155, 53, 220, 107, 185, 110, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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