Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185a2fd8b11345f578632e8c50514afd1dc2451bd9c6ccf60cbad5c1e5ab0115

Tx prefix hash: 858fedc9800cd960bf292e94280ed280d658aedf29107b0ac2fc990b2f79e5fb
Tx public key: 51b3eaa8eee668ff21ee753b69119bffcf8f5d5fae03d2ff232353b907383fe4
Timestamp: 1745905249 Timestamp [UCT]: 2025-04-29 05:40:49 Age [y:d:h:m:s]: 00:211:10:37:21
Block: 1271816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148842 RingCT/type: yes/0
Extra: 0151b3eaa8eee668ff21ee753b69119bffcf8f5d5fae03d2ff232353b907383fe402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05316d7a2b6d49e88ac6e83dfe2df3b082730a820ed3058e618d7c0ea50f772f 0.600000000000 1759083 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": 1271826, "vin": [ { "gen": { "height": 1271816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05316d7a2b6d49e88ac6e83dfe2df3b082730a820ed3058e618d7c0ea50f772f" } } ], "extra": [ 1, 81, 179, 234, 168, 238, 230, 104, 255, 33, 238, 117, 59, 105, 17, 155, 255, 207, 143, 93, 95, 174, 3, 210, 255, 35, 35, 83, 185, 7, 56, 63, 228, 2, 17, 0, 0, 0, 1, 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