Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f9473278bb72e8e0f243bd1a1e2e63a33a724473298e35ca137e56c9819d85

Tx prefix hash: f7ff6f1ec466a8ea95b739f761d51984f68365055cc32b754de7b27797ba9326
Tx public key: 6a63ece3fc847380a4ee2eb1a40470f628515cb74eac17d354a9a58d46878ae0
Timestamp: 1731781141 Timestamp [UCT]: 2024-11-16 18:19:01 Age [y:d:h:m:s]: 00:055:00:06:29
Block: 1155120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39366 RingCT/type: yes/0
Extra: 016a63ece3fc847380a4ee2eb1a40470f628515cb74eac17d354a9a58d46878ae00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfbe40c2e05a2f068e967f4a635b9d23e624089f530f49892dbf6ec6322eeec6 0.600000000000 1640735 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": 1155130, "vin": [ { "gen": { "height": 1155120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfbe40c2e05a2f068e967f4a635b9d23e624089f530f49892dbf6ec6322eeec6" } } ], "extra": [ 1, 106, 99, 236, 227, 252, 132, 115, 128, 164, 238, 46, 177, 164, 4, 112, 246, 40, 81, 92, 183, 78, 172, 23, 211, 84, 169, 165, 141, 70, 135, 138, 224, 2, 17, 0, 0, 0, 2, 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