Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0a2e857facb61fe80c494e223d18fbe8d7c7db7c948f66f3423db72576033c4

Tx prefix hash: 16d65e54082289d0c397f718914bd90945af51748a25e91bed9dfd7d1163e7f3
Tx public key: 1abc5d442c129840f3afe844dccb63dd6e103cf45f2955bc1c51d2bec241f2ea
Timestamp: 1723204342 Timestamp [UCT]: 2024-08-09 11:52:22 Age [y:d:h:m:s]: 00:138:03:03:46
Block: 1084124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98823 RingCT/type: yes/0
Extra: 011abc5d442c129840f3afe844dccb63dd6e103cf45f2955bc1c51d2bec241f2ea02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e9d411a1beb3cc5781f946ebb81b514d0c9971626781c978f34359c319ed174 0.600000000000 1558287 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": 1084134, "vin": [ { "gen": { "height": 1084124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e9d411a1beb3cc5781f946ebb81b514d0c9971626781c978f34359c319ed174" } } ], "extra": [ 1, 26, 188, 93, 68, 44, 18, 152, 64, 243, 175, 232, 68, 220, 203, 99, 221, 110, 16, 60, 244, 95, 41, 85, 188, 28, 81, 210, 190, 194, 65, 242, 234, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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