Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 608be0076a94c507566296090d8f6cb2f795a15dbbe4d9568f9388de5f0399c4

Tx prefix hash: 772f3cb5baff29b59b7672952aa10a626ce15779883a29430a9c509d0dd7ed47
Tx public key: 41bc0d8db6ed9efa9ae9ff65c10cd0edd7a435ec4b167ff57ddc019748be6a2a
Timestamp: 1678514192 Timestamp [UCT]: 2023-03-11 05:56:32 Age [y:d:h:m:s]: 02:039:08:34:49
Block: 714513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549692 RingCT/type: yes/0
Extra: 0141bc0d8db6ed9efa9ae9ff65c10cd0edd7a435ec4b167ff57ddc019748be6a2a0211000000075029cbac000000000000000000

1 output(s) for total of 2.633429611000 dcy

stealth address amount amount idx
00: 11e3648cd5c8e5c289af24b435375b2f702d740f613543c1a69d9df2c2cd3c0d 2.633429611000 1158774 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": 714523, "vin": [ { "gen": { "height": 714513 } } ], "vout": [ { "amount": 2633429611, "target": { "key": "11e3648cd5c8e5c289af24b435375b2f702d740f613543c1a69d9df2c2cd3c0d" } } ], "extra": [ 1, 65, 188, 13, 141, 182, 237, 158, 250, 154, 233, 255, 101, 193, 12, 208, 237, 215, 164, 53, 236, 75, 22, 127, 245, 125, 220, 1, 151, 72, 190, 106, 42, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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