Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce6ff68f43f5c1ad712452cb4a8005b776cd769281d07860195e26517e808999

Tx prefix hash: 86b664626ea1cf4cff4e165ba7af6c9009b1f4958c8704671ee3c0793d67fda5
Tx public key: 24b1952833ea580cc4e85a40251d2d9f0925fd3fb6c4f54892b666e47a0cdf54
Timestamp: 1633644022 Timestamp [UCT]: 2021-10-07 22:00:22 Age [y:d:h:m:s]: 03:086:15:25:45
Block: 348688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 839218 RingCT/type: yes/0
Extra: 0124b1952833ea580cc4e85a40251d2d9f0925fd3fb6c4f54892b666e47a0cdf540211000000043fc41461000000000000000000

1 output(s) for total of 42.919270692000 dcy

stealth address amount amount idx
00: 21c4a4df9f2b4d816562e535b08f9694f3b3b294173d3d36d946cb66411a3d3c 42.919270692000 713996 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": 348698, "vin": [ { "gen": { "height": 348688 } } ], "vout": [ { "amount": 42919270692, "target": { "key": "21c4a4df9f2b4d816562e535b08f9694f3b3b294173d3d36d946cb66411a3d3c" } } ], "extra": [ 1, 36, 177, 149, 40, 51, 234, 88, 12, 196, 232, 90, 64, 37, 29, 45, 159, 9, 37, 253, 63, 182, 196, 245, 72, 146, 182, 102, 228, 122, 12, 223, 84, 2, 17, 0, 0, 0, 4, 63, 196, 20, 97, 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