Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a101d150a854136ee8aa784dd220b767f3d570e60b986d65367176c74ac9e3e

Tx prefix hash: d9492faa1c491d50f7837cb428d5b681ed27ba9c7031b650498cbaa4cec12653
Tx public key: a5aab1e707e03601f687ed9bb4ef1b300a2a8a048b71d53c9008b0579a23f042
Timestamp: 1714832740 Timestamp [UCT]: 2024-05-04 14:25:40 Age [y:d:h:m:s]: 01:034:14:14:10
Block: 1014728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285665 RingCT/type: yes/0
Extra: 01a5aab1e707e03601f687ed9bb4ef1b300a2a8a048b71d53c9008b0579a23f04202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b96d30b55f2cde26f03411eef2da853d3012f0307d4e0494e38e6b8ea3d74f7d 0.600000000000 1477899 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": 1014738, "vin": [ { "gen": { "height": 1014728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b96d30b55f2cde26f03411eef2da853d3012f0307d4e0494e38e6b8ea3d74f7d" } } ], "extra": [ 1, 165, 170, 177, 231, 7, 224, 54, 1, 246, 135, 237, 155, 180, 239, 27, 48, 10, 42, 138, 4, 139, 113, 213, 60, 144, 8, 176, 87, 154, 35, 240, 66, 2, 17, 0, 0, 0, 3, 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