Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79a40341cdd9a777219a7bd5c4a34d0f39b76f3eb0823c03e1021b7981e259f2

Tx prefix hash: 4d4ffc131672587f69c2076ca4027c695e1d33fd52158784f9f338fbb1c5630a
Tx public key: 0a59007476b9eaff8e1d7993cac45fd9e898e211b22b34fe7d6f876f9b4aa9b6
Timestamp: 1704556323 Timestamp [UCT]: 2024-01-06 15:52:03 Age [y:d:h:m:s]: 01:130:18:53:05
Block: 929504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354605 RingCT/type: yes/0
Extra: 010a59007476b9eaff8e1d7993cac45fd9e898e211b22b34fe7d6f876f9b4aa9b602110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a2ace759e2b73e045f88b25394ede491d422879c4a29ba6a9dd9bcd95b561b5 0.600000000000 1387380 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": 929514, "vin": [ { "gen": { "height": 929504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a2ace759e2b73e045f88b25394ede491d422879c4a29ba6a9dd9bcd95b561b5" } } ], "extra": [ 1, 10, 89, 0, 116, 118, 185, 234, 255, 142, 29, 121, 147, 202, 196, 95, 217, 232, 152, 226, 17, 178, 43, 52, 254, 125, 111, 135, 111, 155, 74, 169, 182, 2, 17, 0, 0, 0, 7, 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