Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41e4c8e08434dc760e6be951c75d355d821af33aa830fdb81a5cd206b5553817

Tx prefix hash: 91bc0cb59a4fe5d7f426349c1b9ae9749642013f0fc1b55f6627c280e5bbeadd
Tx public key: b0096433c1c2e2e83104e59cd597f49aed33cab09e514acb56bcb29d3cd9012d
Timestamp: 1750565310 Timestamp [UCT]: 2025-06-22 04:08:30 Age [y:d:h:m:s]: 00:147:13:24:33
Block: 1310202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103323 RingCT/type: yes/0
Extra: 01b0096433c1c2e2e83104e59cd597f49aed33cab09e514acb56bcb29d3cd9012d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 173bcb6c50e80dbd22db231a765f8b573f0fecb908f971f48da4372869c4d4a9 0.600000000000 1797821 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": 1310212, "vin": [ { "gen": { "height": 1310202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "173bcb6c50e80dbd22db231a765f8b573f0fecb908f971f48da4372869c4d4a9" } } ], "extra": [ 1, 176, 9, 100, 51, 193, 194, 226, 232, 49, 4, 229, 156, 213, 151, 244, 154, 237, 51, 202, 176, 158, 81, 74, 203, 86, 188, 178, 157, 60, 217, 1, 45, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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