Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1738f85fa38298f2a6f4243efa4b4d51162a124d7f856ee3f4790e7534b11c

Tx prefix hash: fa29203dca9905851a56d60150d02371de3acea2218720785f34401daadd0306
Tx public key: eec1171c486eb369b4f947d0bb215ca23cd3c8ef8bd938a1a15d2695299f9c03
Timestamp: 1702281033 Timestamp [UCT]: 2023-12-11 07:50:33 Age [y:d:h:m:s]: 02:048:16:27:14
Block: 910657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554442 RingCT/type: yes/0
Extra: 01eec1171c486eb369b4f947d0bb215ca23cd3c8ef8bd938a1a15d2695299f9c03021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18c6efe7a5c65b44253e2a32e5df6b925539a0da1eb8077142da390e6cc0f5cf 0.600000000000 1367822 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": 910667, "vin": [ { "gen": { "height": 910657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18c6efe7a5c65b44253e2a32e5df6b925539a0da1eb8077142da390e6cc0f5cf" } } ], "extra": [ 1, 238, 193, 23, 28, 72, 110, 179, 105, 180, 249, 71, 208, 187, 33, 92, 162, 60, 211, 200, 239, 139, 217, 56, 161, 161, 93, 38, 149, 41, 159, 156, 3, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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