Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9f3ad33eb199a1a2b3f7ed6de938c05a55ad5398bae15e04fdaab0ccb4e86a

Tx prefix hash: ba99ae5c8d3d44072e26869aed1e08a9130d7b8ae1cbc4bf6c43fac7d00372bd
Tx public key: e550b98d047df841c4ba40241661bc3448db6bdac2e2215ad1e109d0f18ea10b
Timestamp: 1761094532 Timestamp [UCT]: 2025-10-22 00:55:32 Age [y:d:h:m:s]: 00:068:13:25:45
Block: 1395138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49082 RingCT/type: yes/0
Extra: 01e550b98d047df841c4ba40241661bc3448db6bdac2e2215ad1e109d0f18ea10b02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a0d4192bb6b6ba4e823d8f6e9a9a1bad2662524a7a976337f7002ae052aebba 0.600000000000 1883415 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": 1395148, "vin": [ { "gen": { "height": 1395138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a0d4192bb6b6ba4e823d8f6e9a9a1bad2662524a7a976337f7002ae052aebba" } } ], "extra": [ 1, 229, 80, 185, 141, 4, 125, 248, 65, 196, 186, 64, 36, 22, 97, 188, 52, 72, 219, 107, 218, 194, 226, 33, 90, 209, 225, 9, 208, 241, 142, 161, 11, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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