Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e02c7e22687d3ea3ff5686f5d9967920475f1a1063f624e9120e106a44f30dd5

Tx prefix hash: c91aad7b6789a019ee6a8097241641eac95c5ddb7b229b175fbc2e96a7312869
Tx public key: f4f8df59393ca59e61421db8fc9ca82d0bb2f0f34b1a0e190716f454235d145a
Timestamp: 1733271492 Timestamp [UCT]: 2024-12-04 00:18:12 Age [y:d:h:m:s]: 00:110:12:59:10
Block: 1167482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78794 RingCT/type: yes/0
Extra: 01f4f8df59393ca59e61421db8fc9ca82d0bb2f0f34b1a0e190716f454235d145a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f509a0e1006471d5c9b97f6cfde873b41739b36fcada1335c7d2418a8f458ffa 0.600000000000 1653179 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": 1167492, "vin": [ { "gen": { "height": 1167482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f509a0e1006471d5c9b97f6cfde873b41739b36fcada1335c7d2418a8f458ffa" } } ], "extra": [ 1, 244, 248, 223, 89, 57, 60, 165, 158, 97, 66, 29, 184, 252, 156, 168, 45, 11, 178, 240, 243, 75, 26, 14, 25, 7, 22, 244, 84, 35, 93, 20, 90, 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