Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866a551fc211992dab4e43e4806cfffcb5b1e4b49ba3b7ed3be1b38dc207c942

Tx prefix hash: 3314ef514854fc05a4eca2be530636fd11cdc2de7542558a518e50b26877855f
Tx public key: 16d3625d47efa4a6fc5bb9eba48e817b654c92e755f15abfd76e04ca5de4cabb
Timestamp: 1721649030 Timestamp [UCT]: 2024-07-22 11:50:30 Age [y:d:h:m:s]: 00:246:06:38:39
Block: 1071222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175929 RingCT/type: yes/0
Extra: 0116d3625d47efa4a6fc5bb9eba48e817b654c92e755f15abfd76e04ca5de4cabb02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8db2fc749e3e4a05e0c5972db5efecc8c8a84981c284f9932885f04671668d16 0.600000000000 1543363 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": 1071232, "vin": [ { "gen": { "height": 1071222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8db2fc749e3e4a05e0c5972db5efecc8c8a84981c284f9932885f04671668d16" } } ], "extra": [ 1, 22, 211, 98, 93, 71, 239, 164, 166, 252, 91, 185, 235, 164, 142, 129, 123, 101, 76, 146, 231, 85, 241, 90, 191, 215, 110, 4, 202, 93, 228, 202, 187, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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