Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c39cceb39e581e15da46541df08b86501e6f67d37ce1c27efe7628d18cc06b7

Tx prefix hash: a0140ffe4a4b05b242de00bdd9bc1849e8d10c32366bca3385e8bac9caa58062
Tx public key: 06f8a50137e5605848205283ac9e99ff71b83c557b729defba6f49ae1d279407
Timestamp: 1754851552 Timestamp [UCT]: 2025-08-10 18:45:52 Age [y:d:h:m:s]: 00:109:13:44:48
Block: 1344303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77542 RingCT/type: yes/0
Extra: 0106f8a50137e5605848205283ac9e99ff71b83c557b729defba6f49ae1d2794070211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd9d67d08ab7a3d9fe87c0fa5bc4a62099cb455d5b0aa433e4f51cf3a0e7428a 0.600000000000 1832186 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": 1344313, "vin": [ { "gen": { "height": 1344303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd9d67d08ab7a3d9fe87c0fa5bc4a62099cb455d5b0aa433e4f51cf3a0e7428a" } } ], "extra": [ 1, 6, 248, 165, 1, 55, 229, 96, 88, 72, 32, 82, 131, 172, 158, 153, 255, 113, 184, 60, 85, 123, 114, 157, 239, 186, 111, 73, 174, 29, 39, 148, 7, 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