Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362883ca9cbbec009d6e0cfab8ed46634fd5a176749cd2d0b128449630b43c6c

Tx prefix hash: 43c423c62a427e309a6dd65d2224119b4e4187db2eba16822cc7de8e1bee096a
Tx public key: 1c00aec214146da209d08b829f9f59f5cf9b7851411dddfc0c574a044d761460
Timestamp: 1729300745 Timestamp [UCT]: 2024-10-19 01:19:05 Age [y:d:h:m:s]: 00:175:15:36:56
Block: 1134662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125317 RingCT/type: yes/0
Extra: 011c00aec214146da209d08b829f9f59f5cf9b7851411dddfc0c574a044d761460021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d16c46c781d61d45c29affe9efc639a2aa3fe1f334652ae1d4b502acf2d945f 0.600000000000 1617987 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": 1134672, "vin": [ { "gen": { "height": 1134662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d16c46c781d61d45c29affe9efc639a2aa3fe1f334652ae1d4b502acf2d945f" } } ], "extra": [ 1, 28, 0, 174, 194, 20, 20, 109, 162, 9, 208, 139, 130, 159, 159, 89, 245, 207, 155, 120, 81, 65, 29, 221, 252, 12, 87, 74, 4, 77, 118, 20, 96, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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