Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4000073fc8e170bb12f8260c269115d0b8fec30ebc3915f7b2761cfebae4e8

Tx prefix hash: 7c8ca4a0a0e0ec55cf6c1341c34607bbc8792d41c1a0a328d21d2c3adb28dccc
Tx public key: a4a0c3dbf2ddaa61ea2efdc9ce79d9cff3ac04992b83f6636bf17a96cc601e21
Timestamp: 1695139405 Timestamp [UCT]: 2023-09-19 16:03:25 Age [y:d:h:m:s]: 01:205:01:19:06
Block: 851639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407632 RingCT/type: yes/0
Extra: 01a4a0c3dbf2ddaa61ea2efdc9ce79d9cff3ac04992b83f6636bf17a96cc601e210211000000084b8f5122000000000000000000

1 output(s) for total of 0.925052785000 dcy

stealth address amount amount idx
00: 02098686490d7e9930bd55cc30e4dc0e0ffddc0151d9ffba610fee1e73232d0d 0.925052785000 1305435 of 0

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": 851649, "vin": [ { "gen": { "height": 851639 } } ], "vout": [ { "amount": 925052785, "target": { "key": "02098686490d7e9930bd55cc30e4dc0e0ffddc0151d9ffba610fee1e73232d0d" } } ], "extra": [ 1, 164, 160, 195, 219, 242, 221, 170, 97, 234, 46, 253, 201, 206, 121, 217, 207, 243, 172, 4, 153, 43, 131, 246, 99, 107, 241, 122, 150, 204, 96, 30, 33, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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