Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c11d989d995c8d4ae9b8771722ff72a40a883b4b1080c2fb5608ed52fd53905

Tx prefix hash: f3bdd9e876cdc3b85ca34a8c788267fb4c2f7ca439afcb78426d7273012cefa4
Tx public key: 5261ca5768edb5b9dc6aa0ba4545be0e7515f33586784f25c6e5bfeda3aca85b
Timestamp: 1698613724 Timestamp [UCT]: 2023-10-29 21:08:44 Age [y:d:h:m:s]: 01:200:10:50:38
Block: 880469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404280 RingCT/type: yes/0
Extra: 015261ca5768edb5b9dc6aa0ba4545be0e7515f33586784f25c6e5bfeda3aca85b021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.742404704000 dcy

stealth address amount amount idx
00: fead07e91d25ccd396a2ce954747395655e20dc4b1599900aa943d33cbdd83d2 0.742404704000 1336027 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": 880479, "vin": [ { "gen": { "height": 880469 } } ], "vout": [ { "amount": 742404704, "target": { "key": "fead07e91d25ccd396a2ce954747395655e20dc4b1599900aa943d33cbdd83d2" } } ], "extra": [ 1, 82, 97, 202, 87, 104, 237, 181, 185, 220, 106, 160, 186, 69, 69, 190, 14, 117, 21, 243, 53, 134, 120, 79, 37, 198, 229, 191, 237, 163, 172, 168, 91, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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