Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ca7c0929aa9c305312d58f6993a1fc9731cea0ccb5f6a244ab306111f02018

Tx prefix hash: 61fba6694f3d28d6a10964b0e63edf367a0ddf309d88117f2d88c94df46bcc32
Tx public key: c1e2fbba27983c8b49e985aed00a8f4ee0b8bbb1a7419f16b9cd6d814057fcf3
Timestamp: 1766098695 Timestamp [UCT]: 2025-12-18 22:58:15 Age [y:d:h:m:s]: 00:003:05:06:37
Block: 1436596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2299 RingCT/type: yes/0
Extra: 01c1e2fbba27983c8b49e985aed00a8f4ee0b8bbb1a7419f16b9cd6d814057fcf3021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5d2a9b3634f4bef38fd77ea95adaa46b13d44aec6b03f0c28f218c5f33b736a 0.600000000000 1925401 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": 1436606, "vin": [ { "gen": { "height": 1436596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5d2a9b3634f4bef38fd77ea95adaa46b13d44aec6b03f0c28f218c5f33b736a" } } ], "extra": [ 1, 193, 226, 251, 186, 39, 152, 60, 139, 73, 233, 133, 174, 208, 10, 143, 78, 224, 184, 187, 177, 167, 65, 159, 22, 185, 205, 109, 129, 64, 87, 252, 243, 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