Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f47a2bddcb37ca3c9f11ceb86cf2a26eb61db7a89e1a4519d1563c1dbe8c5da7

Tx prefix hash: c1c0146139535248aafc124aeb41062494aea21a2c36994c7c8cd9aa0d7201a5
Tx public key: a63dd0a0746cca7c797a1e8eaeff744512b0e43e03590599379996ca3b023218
Timestamp: 1696398500 Timestamp [UCT]: 2023-10-04 05:48:20 Age [y:d:h:m:s]: 02:037:06:01:19
Block: 862081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546265 RingCT/type: yes/0
Extra: 01a63dd0a0746cca7c797a1e8eaeff744512b0e43e03590599379996ca3b023218021100000005faf35c9c000000000000000000

1 output(s) for total of 0.854216231000 dcy

stealth address amount amount idx
00: 2ac946a9b2d0ef1b126c725d0a0042abc5d6ecf4246ea8715db5f876a9d1d9bb 0.854216231000 1316467 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": 862091, "vin": [ { "gen": { "height": 862081 } } ], "vout": [ { "amount": 854216231, "target": { "key": "2ac946a9b2d0ef1b126c725d0a0042abc5d6ecf4246ea8715db5f876a9d1d9bb" } } ], "extra": [ 1, 166, 61, 208, 160, 116, 108, 202, 124, 121, 122, 30, 142, 174, 255, 116, 69, 18, 176, 228, 62, 3, 89, 5, 153, 55, 153, 150, 202, 59, 2, 50, 24, 2, 17, 0, 0, 0, 5, 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