Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38ad11b50199e91a9bd63ed8900b88545ba019e9c153a1257403d21ad6b2f77

Tx prefix hash: 34e3c892a64e8a104b27dfe3eba058d32bfd3a5959848dd3be1803f34df965cc
Tx public key: 7c8c103801b536e6c43191e1ecc49f5445b59b4591c03fcac9869963a6e8b5f3
Timestamp: 1725972447 Timestamp [UCT]: 2024-09-10 12:47:27 Age [y:d:h:m:s]: 00:212:18:01:24
Block: 1107073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151894 RingCT/type: yes/0
Extra: 017c8c103801b536e6c43191e1ecc49f5445b59b4591c03fcac9869963a6e8b5f302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31871e088c9d7671f3a6bf95328034db37a3535bfd3d56bf344df414e8b2204e 0.600000000000 1584680 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": 1107083, "vin": [ { "gen": { "height": 1107073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31871e088c9d7671f3a6bf95328034db37a3535bfd3d56bf344df414e8b2204e" } } ], "extra": [ 1, 124, 140, 16, 56, 1, 181, 54, 230, 196, 49, 145, 225, 236, 196, 159, 84, 69, 181, 155, 69, 145, 192, 63, 202, 201, 134, 153, 99, 166, 232, 181, 243, 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