Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f534c8fdd87e041257aeda0c948a74cd9bdbf983cc37457e2c9c1a7ab324674

Tx prefix hash: b87cdd1e15d8f15963803fb962c7969e2cbdf00b3a0cdfc40b879d3b4e5ae2ae
Tx public key: bf967743870e0a85500a2cf3012a235659a8122a3c93dee98ed14e44d09fce19
Timestamp: 1745676179 Timestamp [UCT]: 2025-04-26 14:02:59 Age [y:d:h:m:s]: 00:209:03:46:43
Block: 1269912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147192 RingCT/type: yes/0
Extra: 01bf967743870e0a85500a2cf3012a235659a8122a3c93dee98ed14e44d09fce1902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec90e52baa9e75df5032cbabeb933cea95010928e2ea7c118d4e8dc02a7eed2 0.600000000000 1757151 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": 1269922, "vin": [ { "gen": { "height": 1269912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec90e52baa9e75df5032cbabeb933cea95010928e2ea7c118d4e8dc02a7eed2" } } ], "extra": [ 1, 191, 150, 119, 67, 135, 14, 10, 133, 80, 10, 44, 243, 1, 42, 35, 86, 89, 168, 18, 42, 60, 147, 222, 233, 142, 209, 78, 68, 208, 159, 206, 25, 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