Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c2218dc673e5d9a4187056d3f61d555831639d533e886d976e63717f16ace6f

Tx prefix hash: 7e3a2b588aea2df49421e3e36db5ea3b4722ea0a83673903e55969e5da053dea
Tx public key: bf408cf17fab6a0e5f1800bec4ad5377934e9c0d3b7ad06513cd40791e25f641
Timestamp: 1706964887 Timestamp [UCT]: 2024-02-03 12:54:47 Age [y:d:h:m:s]: 01:102:06:54:32
Block: 949476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334197 RingCT/type: yes/0
Extra: 01bf408cf17fab6a0e5f1800bec4ad5377934e9c0d3b7ad06513cd40791e25f6410211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b790f276bae33df240339011c9181c21c79541a2da0c8fa3d93c33cd0e675ad6 0.600000000000 1408002 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": 949486, "vin": [ { "gen": { "height": 949476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b790f276bae33df240339011c9181c21c79541a2da0c8fa3d93c33cd0e675ad6" } } ], "extra": [ 1, 191, 64, 140, 241, 127, 171, 106, 14, 95, 24, 0, 190, 196, 173, 83, 119, 147, 78, 156, 13, 59, 122, 208, 101, 19, 205, 64, 121, 30, 37, 246, 65, 2, 17, 0, 0, 0, 2, 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