Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1799a89328b68859e1e0e173ec5f954a6bb13bbd49876d5a4fea2424fca54967

Tx prefix hash: c1f0fb1e56e85381235c3a18e8172a1870263fd9b748dd82d7cc20cdab610b91
Tx public key: 566db6ad29538c2b2ebfe9f5e378deca1ac863fae6c8128102c87b8dee0c2a3e
Timestamp: 1674920854 Timestamp [UCT]: 2023-01-28 15:47:34 Age [y:d:h:m:s]: 01:355:03:40:53
Block: 684690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514838 RingCT/type: yes/0
Extra: 01566db6ad29538c2b2ebfe9f5e378deca1ac863fae6c8128102c87b8dee0c2a3e021100000001faf35c9c000000000000000000

1 output(s) for total of 3.306265591000 dcy

stealth address amount amount idx
00: 1f7f7629bfe901b3805c495839b74d1241aadfef28967098d11d15cb80950de7 3.306265591000 1126959 of 0

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": 684700, "vin": [ { "gen": { "height": 684690 } } ], "vout": [ { "amount": 3306265591, "target": { "key": "1f7f7629bfe901b3805c495839b74d1241aadfef28967098d11d15cb80950de7" } } ], "extra": [ 1, 86, 109, 182, 173, 41, 83, 140, 43, 46, 191, 233, 245, 227, 120, 222, 202, 26, 200, 99, 250, 230, 200, 18, 129, 2, 200, 123, 141, 238, 12, 42, 62, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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