Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7197f32971e2b360694d63267aa842f9736a805e53f0cf84bf02f6d0094e9853

Tx prefix hash: c6afa7e3d2a95a7fb45440b19e4e86e9f5790472c3f4fc0f35085b19632dd0ee
Tx public key: 396d900ecc48d67abce599ca4f9c70a5cfa34acdaea4f1758bc34074cae2e095
Timestamp: 1703569015 Timestamp [UCT]: 2023-12-26 05:36:55 Age [y:d:h:m:s]: 01:126:23:48:45
Block: 921336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351880 RingCT/type: yes/0
Extra: 01396d900ecc48d67abce599ca4f9c70a5cfa34acdaea4f1758bc34074cae2e09502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27b0d80ee89b4b9641b3f4909a1af46c38b328551d5896810654b24a64263a02 0.600000000000 1379022 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": 921346, "vin": [ { "gen": { "height": 921336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27b0d80ee89b4b9641b3f4909a1af46c38b328551d5896810654b24a64263a02" } } ], "extra": [ 1, 57, 109, 144, 14, 204, 72, 214, 122, 188, 229, 153, 202, 79, 156, 112, 165, 207, 163, 74, 205, 174, 164, 241, 117, 139, 195, 64, 116, 202, 226, 224, 149, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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