Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb32f9d8a96231cbc74ff1f277dee8950c56530e7afd61fc0f998244cfc7d2c

Tx prefix hash: 91c1e5c9b644cb3199e8b1e45d7cd3c01a808cac350bee6b2d98e84527bf6429
Tx public key: cbad7a6563b0f8657cf8972338106514d09fb9b1f0f0ef13c840c9261e0cb2e1
Timestamp: 1714381685 Timestamp [UCT]: 2024-04-29 09:08:05 Age [y:d:h:m:s]: 01:192:19:54:23
Block: 1010975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396453 RingCT/type: yes/0
Extra: 01cbad7a6563b0f8657cf8972338106514d09fb9b1f0f0ef13c840c9261e0cb2e10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49b85dd048671f9c69c28bc4f3d81a867144bcd49000fe5bbb9c2b1238f2bfd3 0.600000000000 1473073 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": 1010985, "vin": [ { "gen": { "height": 1010975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49b85dd048671f9c69c28bc4f3d81a867144bcd49000fe5bbb9c2b1238f2bfd3" } } ], "extra": [ 1, 203, 173, 122, 101, 99, 176, 248, 101, 124, 248, 151, 35, 56, 16, 101, 20, 208, 159, 185, 177, 240, 240, 239, 19, 200, 64, 201, 38, 30, 12, 178, 225, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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