Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59b69d26a5b81c1b18c555abac51c28287f149a60143c9e1303efc4d0e67ef7

Tx prefix hash: 66c4239dfe4942c8fcc7fe7eb34d2588328b43ba5a4770597b3f54077e0d794b
Tx public key: 3f43a5a0d6117e7ee98ce02fcd3b1c8e5d3b340b5b669d2e45b811bf4f4621b8
Timestamp: 1705032549 Timestamp [UCT]: 2024-01-12 04:09:09 Age [y:d:h:m:s]: 01:079:08:17:39
Block: 933448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317816 RingCT/type: yes/0
Extra: 013f43a5a0d6117e7ee98ce02fcd3b1c8e5d3b340b5b669d2e45b811bf4f4621b80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d56c2715eff4494912f4dce124bc078d13eac1ae06104cfb76ec22f6898316 0.600000000000 1391410 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": 933458, "vin": [ { "gen": { "height": 933448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d56c2715eff4494912f4dce124bc078d13eac1ae06104cfb76ec22f6898316" } } ], "extra": [ 1, 63, 67, 165, 160, 214, 17, 126, 126, 233, 140, 224, 47, 205, 59, 28, 142, 93, 59, 52, 11, 91, 102, 157, 46, 69, 184, 17, 191, 79, 70, 33, 184, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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