Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e77c80d0d72c0cd4969b5b57158531fe9adfb49148bff93bed2709cf18f3ed2

Tx prefix hash: a300fb18f6d4f30b42d2297a0621d2e5efa7e4ac1f00f79fd96a289076702240
Tx public key: 1ea3f14cbac7d8628a89ad8f5e43f5f906ae54350c8e5fd22ca1cef31ec16f8c
Timestamp: 1580776822 Timestamp [UCT]: 2020-02-04 00:40:22 Age [y:d:h:m:s]: 04:276:13:26:26
Block: 57958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089173 RingCT/type: yes/0
Extra: 011ea3f14cbac7d8628a89ad8f5e43f5f906ae54350c8e5fd22ca1cef31ec16f8c02110000000d4943cd9f000000000000000000

1 output(s) for total of 394.422705544000 dcy

stealth address amount amount idx
00: 90040053acd34f3edc437e4d0fc2964d5c3f08a8067d44f0d284aee1d89ec576 394.422705544000 107201 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": 57968, "vin": [ { "gen": { "height": 57958 } } ], "vout": [ { "amount": 394422705544, "target": { "key": "90040053acd34f3edc437e4d0fc2964d5c3f08a8067d44f0d284aee1d89ec576" } } ], "extra": [ 1, 30, 163, 241, 76, 186, 199, 216, 98, 138, 137, 173, 143, 94, 67, 245, 249, 6, 174, 84, 53, 12, 142, 95, 210, 44, 161, 206, 243, 30, 193, 111, 140, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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