Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ec9872834dc60b67ca9dc9dba4253a610435a4b606d96ed43d7570e02a19a3

Tx prefix hash: 13600f617e98d1dea5caabb3da639b0e224bbf745ccc3ef35d69bf404833a3ed
Tx public key: 0e92494f143b7dc2c2f2a30b988547c576824042f835e05656bfa4991ba6791a
Timestamp: 1712876375 Timestamp [UCT]: 2024-04-11 22:59:35 Age [y:d:h:m:s]: 01:009:19:51:06
Block: 998472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267996 RingCT/type: yes/0
Extra: 010e92494f143b7dc2c2f2a30b988547c576824042f835e05656bfa4991ba6791a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 126dcb8dc7a0f2b9e377b1e29a08e8119dd5bf75b1815f4c8577c1f8edb209ea 0.600000000000 1458922 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": 998482, "vin": [ { "gen": { "height": 998472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "126dcb8dc7a0f2b9e377b1e29a08e8119dd5bf75b1815f4c8577c1f8edb209ea" } } ], "extra": [ 1, 14, 146, 73, 79, 20, 59, 125, 194, 194, 242, 163, 11, 152, 133, 71, 197, 118, 130, 64, 66, 248, 53, 224, 86, 86, 191, 164, 153, 27, 166, 121, 26, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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