Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8ca7a1f4f420fab3e7b24bf22e891a8929cfae9a24b395bfe8c35de523ebbb

Tx prefix hash: d7c6035535adbe5d62710ce2dc47cc2ff52bd5f96899b7d8ac957c7f03f9ccef
Tx public key: 9712bf3bd9b7d5a719f68b429ddc7ac453ba5f8fa579a086417b2be0ad4d3e0b
Timestamp: 1745751243 Timestamp [UCT]: 2025-04-27 10:54:03 Age [y:d:h:m:s]: 00:053:14:25:59
Block: 1270535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38193 RingCT/type: yes/0
Extra: 019712bf3bd9b7d5a719f68b429ddc7ac453ba5f8fa579a086417b2be0ad4d3e0b0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34843a64290f0640432db947dddaa1c39d5ef4edc16be0bfe1c0acd844c556ea 0.600000000000 1757778 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": 1270545, "vin": [ { "gen": { "height": 1270535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34843a64290f0640432db947dddaa1c39d5ef4edc16be0bfe1c0acd844c556ea" } } ], "extra": [ 1, 151, 18, 191, 59, 217, 183, 213, 167, 25, 246, 139, 66, 157, 220, 122, 196, 83, 186, 95, 143, 165, 121, 160, 134, 65, 123, 43, 224, 173, 77, 62, 11, 2, 17, 0, 0, 0, 4, 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