Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454c78577326947cf921d11494ac997acc5077f61d65d2401f25c70a65885ab5

Tx prefix hash: 99ad9c102d24ed6e4b80870e1b2c85674651bc068619c7ac780d4574d666d087
Tx public key: b9088b9807af60c0860364b5d3867f69116a0c041de4d7c1cd5d5be2c50f6135
Timestamp: 1695596607 Timestamp [UCT]: 2023-09-24 23:03:27 Age [y:d:h:m:s]: 01:186:09:29:02
Block: 855439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394275 RingCT/type: yes/0
Extra: 01b9088b9807af60c0860364b5d3867f69116a0c041de4d7c1cd5d5be2c50f6135021100000003faf35c9c000000000000000000

1 output(s) for total of 0.898618866000 dcy

stealth address amount amount idx
00: 4c40bbcad919928b5b3c5895c97d653d96d3dbd190dc0121cec20a08e2517385 0.898618866000 1309461 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": 855449, "vin": [ { "gen": { "height": 855439 } } ], "vout": [ { "amount": 898618866, "target": { "key": "4c40bbcad919928b5b3c5895c97d653d96d3dbd190dc0121cec20a08e2517385" } } ], "extra": [ 1, 185, 8, 139, 152, 7, 175, 96, 192, 134, 3, 100, 181, 211, 134, 127, 105, 17, 106, 12, 4, 29, 228, 215, 193, 205, 93, 91, 226, 197, 15, 97, 53, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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