Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42c00e5488874565e0794073171d7f2ea23e2ff5ea2d3b7cb7792d9c030e3767

Tx prefix hash: 129733cdbea1a14f55618e9797ee27acd41e82fc804874661059e1db8d45d12f
Tx public key: 32e69add6a7197ff364d90506a387f95f44e2bbd55dff582ed963c33d6661468
Timestamp: 1712299337 Timestamp [UCT]: 2024-04-05 06:42:17 Age [y:d:h:m:s]: 00:347:13:56:25
Block: 993687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248537 RingCT/type: yes/0
Extra: 0132e69add6a7197ff364d90506a387f95f44e2bbd55dff582ed963c33d666146802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e25b6b74da450e09e18a936c55268fbfb373b72ead28c4d53e811c896fbea1 0.600000000000 1454075 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": 993697, "vin": [ { "gen": { "height": 993687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e25b6b74da450e09e18a936c55268fbfb373b72ead28c4d53e811c896fbea1" } } ], "extra": [ 1, 50, 230, 154, 221, 106, 113, 151, 255, 54, 77, 144, 80, 106, 56, 127, 149, 244, 78, 43, 189, 85, 223, 245, 130, 237, 150, 60, 51, 214, 102, 20, 104, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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