Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c8d17a5833dbba071a0f07a129e0582970b40a7573155eb03d9f52117222b56

Tx prefix hash: b14270ffaf6d0f022b5f7b9fa2ef4eda9f2e1b7c7041fe805196536cc7380174
Tx public key: 89fa5ba4c38643776815e51a238e447a39c716470b097a8743aebba422d3cf9b
Timestamp: 1732912784 Timestamp [UCT]: 2024-11-29 20:39:44 Age [y:d:h:m:s]: 00:115:14:36:52
Block: 1164506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82430 RingCT/type: yes/0
Extra: 0189fa5ba4c38643776815e51a238e447a39c716470b097a8743aebba422d3cf9b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c7a77d1b5b0064acdf180b39cb221d26fc69abd263e67a7f2086b6e352cb55 0.600000000000 1650179 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": 1164516, "vin": [ { "gen": { "height": 1164506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c7a77d1b5b0064acdf180b39cb221d26fc69abd263e67a7f2086b6e352cb55" } } ], "extra": [ 1, 137, 250, 91, 164, 195, 134, 67, 119, 104, 21, 229, 26, 35, 142, 68, 122, 57, 199, 22, 71, 11, 9, 122, 135, 67, 174, 187, 164, 34, 211, 207, 155, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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