Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3897751a9d4e222532d93d2524e94e625e3539a933c6e84349c80b361f2d1000

Tx prefix hash: cf4ff7c6bdf0c77f0957e122b9752432c440f8c37c0fd20b74492485e937f887
Tx public key: cc7a94d9d416891cbe23a5c978761b39e356f84609a555429b2e8bed16e9b0bf
Timestamp: 1703685929 Timestamp [UCT]: 2023-12-27 14:05:29 Age [y:d:h:m:s]: 01:015:06:49:30
Block: 922305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272258 RingCT/type: yes/0
Extra: 01cc7a94d9d416891cbe23a5c978761b39e356f84609a555429b2e8bed16e9b0bf02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b55cd60a0c38404deb55b55734123576a02ba7ed7178c64e8e1e5fc0b5059ca8 0.600000000000 1380001 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": 922315, "vin": [ { "gen": { "height": 922305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b55cd60a0c38404deb55b55734123576a02ba7ed7178c64e8e1e5fc0b5059ca8" } } ], "extra": [ 1, 204, 122, 148, 217, 212, 22, 137, 28, 190, 35, 165, 201, 120, 118, 27, 57, 227, 86, 248, 70, 9, 165, 85, 66, 155, 46, 139, 237, 22, 233, 176, 191, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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