Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71586c650fa7f10b26c107ff1b9f14e094938af45a5446bba10190fc30d1c763

Tx prefix hash: 35d7f4e31edc19d63d34be5159c56a3f73213941a6c28466f45d1408a1ed4bbf
Tx public key: 5f8db071738f123c305fed6bef2b219dc0a65c1be9f3473b85ccfc175503bcb0
Timestamp: 1718238190 Timestamp [UCT]: 2024-06-13 00:23:10 Age [y:d:h:m:s]: 00:275:15:36:04
Block: 1042954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196989 RingCT/type: yes/0
Extra: 015f8db071738f123c305fed6bef2b219dc0a65c1be9f3473b85ccfc175503bcb00211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d054487de3a85df0b3de71d5471ff49d5d65cb36dfd8e14e45b04bd9fb868e6 0.600000000000 1511989 of 15

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": 1042964, "vin": [ { "gen": { "height": 1042954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d054487de3a85df0b3de71d5471ff49d5d65cb36dfd8e14e45b04bd9fb868e6" } } ], "extra": [ 1, 95, 141, 176, 113, 115, 143, 18, 60, 48, 95, 237, 107, 239, 43, 33, 157, 192, 166, 92, 27, 233, 243, 71, 59, 133, 204, 252, 23, 85, 3, 188, 176, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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