Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e057c18e2b048809c636f317ae93fccf33b8f40e1188b655170b1f50b099e89c

Tx prefix hash: f767fe20677cb1c99a79c1b7ff99244f70bd9f33dcf59c9ccccb3fd1d72d49fb
Tx public key: 58a91d251e501af57720016e8b8245591094396f03ada971c4c580d1403d1574
Timestamp: 1728111734 Timestamp [UCT]: 2024-10-05 07:02:14 Age [y:d:h:m:s]: 00:194:03:05:34
Block: 1124800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138546 RingCT/type: yes/0
Extra: 0158a91d251e501af57720016e8b8245591094396f03ada971c4c580d1403d1574021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e86f161130f3b9c5d28f59c0efdf982fb9e63003f0aa7208297e21f35604fcd 0.600000000000 1607469 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": 1124810, "vin": [ { "gen": { "height": 1124800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e86f161130f3b9c5d28f59c0efdf982fb9e63003f0aa7208297e21f35604fcd" } } ], "extra": [ 1, 88, 169, 29, 37, 30, 80, 26, 245, 119, 32, 1, 110, 139, 130, 69, 89, 16, 148, 57, 111, 3, 173, 169, 113, 196, 197, 128, 209, 64, 61, 21, 116, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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