Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f8f2fb0bfbd84199e3e3caf7241a6b4018ef257fd9384e296484a607fbca460

Tx prefix hash: 46a13c07b36badbe5f913f9ee39e49c68d793e9a1f127941c11be0177ad50f1e
Tx public key: 132cb12936fd6ef8b439993c2d9e49684c5263167412095e5e0c825a6564d7e5
Timestamp: 1756394572 Timestamp [UCT]: 2025-08-28 15:22:52 Age [y:d:h:m:s]: 00:073:12:49:21
Block: 1356365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52469 RingCT/type: yes/0
Extra: 01132cb12936fd6ef8b439993c2d9e49684c5263167412095e5e0c825a6564d7e50211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff9c74d877d8b06ce18cca829da3d4da73d768b93824359eaf75cd2dafa4dd82 0.600000000000 1844372 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": 1356375, "vin": [ { "gen": { "height": 1356365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff9c74d877d8b06ce18cca829da3d4da73d768b93824359eaf75cd2dafa4dd82" } } ], "extra": [ 1, 19, 44, 177, 41, 54, 253, 110, 248, 180, 57, 153, 60, 45, 158, 73, 104, 76, 82, 99, 22, 116, 18, 9, 94, 94, 12, 130, 90, 101, 100, 215, 229, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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