Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28604a0ff1459a28946500bba5b1edf9b99062fd94655e98e562cd8822c4d055

Tx prefix hash: bd64a9b8effd57596e44affd7ead70905d302fdd5d8fb252c503041c50c3f3c8
Tx public key: 5cc091bb49aac193d39a9f44d633d39d4fba58a0da94597489880771240d61e2
Timestamp: 1580570455 Timestamp [UCT]: 2020-02-01 15:20:55 Age [y:d:h:m:s]: 04:326:15:37:31
Block: 56670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124632 RingCT/type: yes/0
Extra: 015cc091bb49aac193d39a9f44d633d39d4fba58a0da94597489880771240d61e20211000000034ac5aa02000000000000000000

1 output(s) for total of 398.353114261000 dcy

stealth address amount amount idx
00: bcbc843afe84d05be2474b71063f9ea5d89bc96826728eb96b5991317b533ce5 398.353114261000 104455 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": 56680, "vin": [ { "gen": { "height": 56670 } } ], "vout": [ { "amount": 398353114261, "target": { "key": "bcbc843afe84d05be2474b71063f9ea5d89bc96826728eb96b5991317b533ce5" } } ], "extra": [ 1, 92, 192, 145, 187, 73, 170, 193, 147, 211, 154, 159, 68, 214, 51, 211, 157, 79, 186, 88, 160, 218, 148, 89, 116, 137, 136, 7, 113, 36, 13, 97, 226, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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