Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fceb0aaaa7356d7180c41fde383ecff711281f32d85be4b12c5612b4b2f8ac88

Tx prefix hash: 68a123f19f516070b6e1185d58b16eacd9b9c87afca2b6a75be75b94cfa25460
Tx public key: 4554a1f99bc610198aec00f771e16bca017c3a1d941dccb9dbb26b0f95af0811
Timestamp: 1707990890 Timestamp [UCT]: 2024-02-15 09:54:50 Age [y:d:h:m:s]: 01:266:17:16:11
Block: 957988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449385 RingCT/type: yes/0
Extra: 014554a1f99bc610198aec00f771e16bca017c3a1d941dccb9dbb26b0f95af081102110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56aef8f4f7e57d3983f75bd0c45241a58cd9615293fde8713d9b349efa7a9ab2 0.600000000000 1417339 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": 957998, "vin": [ { "gen": { "height": 957988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56aef8f4f7e57d3983f75bd0c45241a58cd9615293fde8713d9b349efa7a9ab2" } } ], "extra": [ 1, 69, 84, 161, 249, 155, 198, 16, 25, 138, 236, 0, 247, 113, 225, 107, 202, 1, 124, 58, 29, 148, 29, 204, 185, 219, 178, 107, 15, 149, 175, 8, 17, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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