Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13c2a0cb68ee2c9716b84ce06871217ad8832d60f92341cfc8a5d75fb6faf1d

Tx prefix hash: 7cc8cccc4453fba2d0f8fc8fa8ddce98038323468a5e0600747b0db1f30762ad
Tx public key: 99daa6c9674d063a012626f8f3c46e85fbe3455112240920ba03cac08a09d83f
Timestamp: 1736234234 Timestamp [UCT]: 2025-01-07 07:17:14 Age [y:d:h:m:s]: 00:091:07:38:47
Block: 1192016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65038 RingCT/type: yes/0
Extra: 0199daa6c9674d063a012626f8f3c46e85fbe3455112240920ba03cac08a09d83f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12e3e6d065ec6c129a7e2eec04f57e543f879ee47e42bdba7c31dc7b9e47a3a3 0.600000000000 1678561 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": 1192026, "vin": [ { "gen": { "height": 1192016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12e3e6d065ec6c129a7e2eec04f57e543f879ee47e42bdba7c31dc7b9e47a3a3" } } ], "extra": [ 1, 153, 218, 166, 201, 103, 77, 6, 58, 1, 38, 38, 248, 243, 196, 110, 133, 251, 227, 69, 81, 18, 36, 9, 32, 186, 3, 202, 192, 138, 9, 216, 63, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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