Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d6808f98227dba41315e67997b5401e06891ccef74b2e6f92f0314630233f80

Tx prefix hash: eb96fa66a370ab7f2bece9d752714543d533e96f244b23393fc73520b0b86647
Tx public key: 0e1177f3fdafdb1791cb0fb4730a2080a3b8650fb95a5882685dbcd70de5c5c7
Timestamp: 1709689166 Timestamp [UCT]: 2024-03-06 01:39:26 Age [y:d:h:m:s]: 01:008:22:59:04
Block: 972083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267400 RingCT/type: yes/0
Extra: 010e1177f3fdafdb1791cb0fb4730a2080a3b8650fb95a5882685dbcd70de5c5c70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642e2ba5d58c682f16984f2444331a0a0d10fcfdbf133c0d29adb6cbae0c517b 0.600000000000 1431988 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": 972093, "vin": [ { "gen": { "height": 972083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642e2ba5d58c682f16984f2444331a0a0d10fcfdbf133c0d29adb6cbae0c517b" } } ], "extra": [ 1, 14, 17, 119, 243, 253, 175, 219, 23, 145, 203, 15, 180, 115, 10, 32, 128, 163, 184, 101, 15, 185, 90, 88, 130, 104, 93, 188, 215, 13, 229, 197, 199, 2, 17, 0, 0, 0, 1, 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