Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de96213e9f1a526debfe6828464223a6b546e785ed9099e5674cc8564067d64

Tx prefix hash: 3881d953d9b35430e6c412725f2a15ee4a3afffd5d2a8c832d6b5fbbaadda4d2
Tx public key: 20ae7076f0e241e0b0ea44149c1f906415e87af07a130f15d4664d3da387b56b
Timestamp: 1708982905 Timestamp [UCT]: 2024-02-26 21:28:25 Age [y:d:h:m:s]: 00:338:09:41:48
Block: 966228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241972 RingCT/type: yes/0
Extra: 0120ae7076f0e241e0b0ea44149c1f906415e87af07a130f15d4664d3da387b56b0211000000030546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3bd1906cc0c492c5eceaf60d109a23299961cc8239358dc01f1bae6b276c254 0.600000000000 1425985 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": 966238, "vin": [ { "gen": { "height": 966228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3bd1906cc0c492c5eceaf60d109a23299961cc8239358dc01f1bae6b276c254" } } ], "extra": [ 1, 32, 174, 112, 118, 240, 226, 65, 224, 176, 234, 68, 20, 156, 31, 144, 100, 21, 232, 122, 240, 122, 19, 15, 21, 212, 102, 77, 61, 163, 135, 181, 107, 2, 17, 0, 0, 0, 3, 5, 70, 215, 208, 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