Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d19af0cbbb20d1284900ffae8d90b1eba34adb9c3cf751113721494eb4733d

Tx prefix hash: f70831bd4c6cefd044d95a7944f7203de7b63d60181533d0b64de345324abf52
Tx public key: 5b28cac7e1547b00b381f841cb7944e9a9d75bc28c4662391d5a38eeb46e9e95
Timestamp: 1756051720 Timestamp [UCT]: 2025-08-24 16:08:40 Age [y:d:h:m:s]: 00:093:21:27:51
Block: 1353519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67048 RingCT/type: yes/0
Extra: 015b28cac7e1547b00b381f841cb7944e9a9d75bc28c4662391d5a38eeb46e9e950211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66ecd9e341e9749a1f38365c7e27e31b3d862c8913f6f92625cf9467aa142256 0.600000000000 1841494 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": 1353529, "vin": [ { "gen": { "height": 1353519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ecd9e341e9749a1f38365c7e27e31b3d862c8913f6f92625cf9467aa142256" } } ], "extra": [ 1, 91, 40, 202, 199, 225, 84, 123, 0, 179, 129, 248, 65, 203, 121, 68, 233, 169, 215, 91, 194, 140, 70, 98, 57, 29, 90, 56, 238, 180, 110, 158, 149, 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