Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7db05f559455ca381d8dcc93bf1663e0d4cac5fcd94f1e1451f8093a44774f5b

Tx prefix hash: e52c0051aa4aa55ef60211312176dd473775401aba93dc3f3f91926c61e87c89
Tx public key: 6f12102d43512aca25c888c336b21edfb8aa2517ef91131566c4d94846ac4006
Timestamp: 1580764539 Timestamp [UCT]: 2020-02-03 21:15:39 Age [y:d:h:m:s]: 04:300:18:28:09
Block: 57921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106439 RingCT/type: yes/0
Extra: 016f12102d43512aca25c888c336b21edfb8aa2517ef91131566c4d94846ac40060211000000068a2ee0d9000000000000000000

1 output(s) for total of 394.534062323000 dcy

stealth address amount amount idx
00: a95a20e815cb9217c2e2dea73a1758a6e59b3ff99ba50f3ea9fe82d81f750bef 394.534062323000 107116 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": 57931, "vin": [ { "gen": { "height": 57921 } } ], "vout": [ { "amount": 394534062323, "target": { "key": "a95a20e815cb9217c2e2dea73a1758a6e59b3ff99ba50f3ea9fe82d81f750bef" } } ], "extra": [ 1, 111, 18, 16, 45, 67, 81, 42, 202, 37, 200, 136, 195, 54, 178, 30, 223, 184, 170, 37, 23, 239, 145, 19, 21, 102, 196, 217, 72, 70, 172, 64, 6, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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