Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 568ca6faaff776add7d760915ca954c72ab4788ce9d2afbd11493425692023bb

Tx prefix hash: b8a45e574843fcca00d9cde417ed090f353882dce0c55cb188bb3d2b8fd88487
Tx public key: 26bcbafdeaff2a2b6375cb511c1c7fec1ed0d131e8153ae785f7f3d34f2fbd33
Timestamp: 1706957134 Timestamp [UCT]: 2024-02-03 10:45:34 Age [y:d:h:m:s]: 01:130:04:28:42
Block: 949404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354126 RingCT/type: yes/0
Extra: 0126bcbafdeaff2a2b6375cb511c1c7fec1ed0d131e8153ae785f7f3d34f2fbd330211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6d0a113f6e0a4c8042cdbc9082c29e841246c8825daee50f95c8505985f307e 0.600000000000 1407928 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": 949414, "vin": [ { "gen": { "height": 949404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6d0a113f6e0a4c8042cdbc9082c29e841246c8825daee50f95c8505985f307e" } } ], "extra": [ 1, 38, 188, 186, 253, 234, 255, 42, 43, 99, 117, 203, 81, 28, 28, 127, 236, 30, 208, 209, 49, 232, 21, 58, 231, 133, 247, 243, 211, 79, 47, 189, 51, 2, 17, 0, 0, 0, 5, 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