Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ddf08457d894421ab014c2042de527f09f63c47b90808052f2189be5f0262c

Tx prefix hash: cb9547ec09daaa77bd5b758b8516d851ecccff19845b8fa7d2ef2d37d75231bb
Tx public key: c993a7a44f832dfa7c5b6ac209385ac1e77fe52b0b7ec747d88a20a0d21bcae0
Timestamp: 1724436174 Timestamp [UCT]: 2024-08-23 18:02:54 Age [y:d:h:m:s]: 01:075:17:52:58
Block: 1094348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312571 RingCT/type: yes/0
Extra: 01c993a7a44f832dfa7c5b6ac209385ac1e77fe52b0b7ec747d88a20a0d21bcae002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0afcfe51a735443ee98b2d31fe308c70c38229d8d6f9854e381ddb11155222e3 0.600000000000 1569465 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": 1094358, "vin": [ { "gen": { "height": 1094348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0afcfe51a735443ee98b2d31fe308c70c38229d8d6f9854e381ddb11155222e3" } } ], "extra": [ 1, 201, 147, 167, 164, 79, 131, 45, 250, 124, 91, 106, 194, 9, 56, 90, 193, 231, 127, 229, 43, 11, 126, 199, 71, 216, 138, 32, 160, 210, 27, 202, 224, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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