Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e553d676ad59d12e5507850bf40068c93b16e89b7379b1f5e6bf593fbb8538

Tx prefix hash: 4a4adffcd9be5a3dfc48e178941951f1cff4ef92a2872bae15fc390e01c06499
Tx public key: 69100283b2e3c5bec0e129a966423619f0c58e0dd210e0c1bb99b26ceac3e750
Timestamp: 1731971084 Timestamp [UCT]: 2024-11-18 23:04:44 Age [y:d:h:m:s]: 00:139:08:57:34
Block: 1156706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99421 RingCT/type: yes/0
Extra: 0169100283b2e3c5bec0e129a966423619f0c58e0dd210e0c1bb99b26ceac3e750021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da6e0370fb1a3c913af4847b7e6ab0ddc328812b959862efaa4a922b4c7e0e38 0.600000000000 1642329 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": 1156716, "vin": [ { "gen": { "height": 1156706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da6e0370fb1a3c913af4847b7e6ab0ddc328812b959862efaa4a922b4c7e0e38" } } ], "extra": [ 1, 105, 16, 2, 131, 178, 227, 197, 190, 192, 225, 41, 169, 102, 66, 54, 25, 240, 197, 142, 13, 210, 16, 224, 193, 187, 153, 178, 108, 234, 195, 231, 80, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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